Redirection of message from mobile station based on identity of mobile station

ABSTRACT

An application service utilizes a single short code for messaging service through a mobile network, even though the one service is actually supported by multiple servers or the like, typically operated by different service providers. In the examples, a third party application service type platform is associated with the common short code of the application service. The third party platform performs intelligent routing/address changes to re-direct mobile station originated messages among the equipment of the service providers. The platform may also provide short code translations of source addresses, during processing of messages directed to mobile stations from the various application servers.

TECHNICAL FIELD

The present subject matter relates to techniques and equipment toredirect mobile originated mobile messaging service messagescommunicated to/from application service provider equipment, based onmobile station identity, for example, to allow such messages that mayuse the same short code that identifies a particular application serviceto be selectively routed among multiple service providers effectivelysharing the same short code for one application service.

BACKGROUND

In recent years, mobile wireless communications have become increasinglypopular. Initial implementations of mobile wireless communications, forexample in the form of cellular telephone networks, supported circuitswitched voice communication services. Mobile voice telephonecommunication is now ubiquitous in many countries, and mobile servicesare replacing fixed landline service even for traditional voicetelephone calls. However, for many years now the mobile serviceofferings have extended far beyond the traditional voice telephone callmodel.

For example, the mobile carriers developed short messaging service (SMS)technology to provide text and/or email communications via the wirelesscommunication networks. As the public wireless communication networkshave evolved to provide greater bandwidth and packet based services, theindustry has developed a variety of data services, such as web browsing,as well as a variety of services using multimedia messaging service(MMS) technology. Many of the messaging services such as SMS and MMSsupport message traffic between mobile stations, e.g. for messageexchange between users. However, these popular messaging services alsosupport traffic between mobile stations and server equipment from whichservice providers offer users a variety of different types ofapplication services.

In a public wireless mobile communication network that offers one ormore of the SMS or MMS type messaging services, each wireless subscriberdevice typically is assigned a valid telephone number, often referred toas a Mobile Directory Number or MDN. The MDN, for example, is used as adestination address to terminate call routing for call delivery and/orfor message delivery. The MDN may also be used to identify thesubscriber and verify subscription profile information duringcommunications through the network.

A mobile messaging service type message, such an SMS message, includessource and destination address fields. For messages from a user device,the source address is the mobile directory number (MDN) of the sendinguser's mobile station. The destination address may be a MDN of adestination station or some other form of recognizable address. Of notefor purposes of this discussion, when the message relates to aparticular application service, the destination address is an address ofthe server equipment hosting the application, typically, in the form ofa short code assigned to the particular application.

If the message originates at such an application server, the destinationaddress would be a MDN of an intended mobile station destination, andthe source address would be the short code assigned to the applicationservice or the service provider. For a message addressed to a mobilestation, the network routes the message based on the MDN of the intendeddestination as the routing address, that is to say all the way throughto the addressed mobile station. For a message addressed to a serviceprovider, the mobile station initially inserts the short code in themessage as the destination address. However, the network translates thesource short code in the message into an actual destination address,such as an Internet Protocol (IP) address of the appropriate server,replaces the short code with the translated address, and routes themessage to the server based on the translated address.

With these address and routing techniques, one source address (MDN orshort code) is used to route each message to one correspondingdestination. However, there are situations where it may be desirable tovary the routing or redirect a message to an alternate destination,including variations with regard to multiple destinations and/or sourceson the application service side. Past proposals for redirection orforwarding have addressed SMS messages addressed to the mobile stations.For example, U.S. Pat. No. 7,319,880 describes one method for forwardingSMS messages addressed to the mobile stations, although the alternatedestination may be another “on network” mobile terminal or may be “offnetwork” such as a mobile terminal on another network or a phone orother device at a public switched telephone network (PSTN) destination.This type of approach does not really address situations relating tomultiple application service providers, e.g. providing the same servicebut using separate equipment. Also, it appears the network's messagecenters are the key elements for resolving the location of theforwarding destination. As the number of messaging service messagescarried by mobile communications networks continues to increase, theburden placed on the messaging service centers also increases. Resolvingthe message forwarding destination at the message center may decreasethe center's ability to provide other services, e.g. related to itsbasic message storage and delivery functions.

However, there are situations when the forwarding or redirection ofmessages may actually relate to messages from mobile devices directedtoward the application service provider(s), and scenarios that give riseto a need for redirection of messages addressed to such serviceproviders may also create issues regarding messages coming from themultiple service providers. To understand these types of concerns, itmay be helpful to consider a specific application service that hasencountered these kinds of message addressing and routing problems.

In recent years, automotive companies and their partners have developedincreasingly sophisticated telematics systems to detect an emergencycondition or activation, and in response, initiate a call to a callcenter for assistance. Similar systems have also been developed formonitoring fixed customer premises locations or personnel at a specificsite. For motor vehicle applications, for example, an on-board systemmonitors one or more sensors to determine when a crash or otheremergency has occurred. Upon detecting an emergency condition, such as acrash, the on-board system activates a cellular transceiver to initiatea cellular communications with a call center of the telematics serviceprovider (TSP). Although a voice call typically is provided, thecommunications include a data communication of information such aslocation determined by global positioning satellite (GPS) processing,identification data and crash related data. The voice call may followthe data transmission, essentially using the same communicationresources through the network. However, some implementations useexisting mobile network messaging services, such as SMS, to provide therequisite data communications for the telematics service.

In the emergency report type telematics service outlined above, themobile device of the telematics unit in the vehicle sends one or moremessages, typically using SMS, using a short code assigned to thetelematics service. The mobile network routes each such message to atelematics service provider, typically to a data server associated withthe provider's call center, in the same manner as any other upstreammessage transmission to an application service provider. In addition tothe emergency reporting services, the call center service providers havestarted offering services that involve downstream data transmissions tothe mobile device in the vehicle, such as turn-by-turn directions. Theserver of the provider sends each message addressed to the mobiledevice, typically using the MDN of the mobile device as the destinationaddress and the short code of the provider/application as the sourceaddress, as in other application services that utilize SMS and/or MMStype delivery services. A situation has arisen, however, in whichservices corresponding to one short code are actually supported by twodifferent service providers and their associated server and call centerequipment.

An auto company Auto-CO offers telematics service to end-user owners oftheir vehicles. The Auto-CO initially utilizes a company CO-A to providethe call center service but wants to change to a second vendor we willcall company CO-B. Due to contractual obligations to service providerCO-A, for a time, at least some of the existing customers will stay withcompany CO-A but new customers' service will go to company CO-B. Thispresents a problem because all of the devices currently send all of themessages from the vehicles to CO-A, using a single address, e.g. asingle short code assigned to the server(s) of company CO-A. Whencompany CO-B comes on line, the SMS messages from some devices need tobe routed to the server or servers for CO-B, but some still need to goto equipment of service provider CO-A, even though the messages will allbe addressed to the same location or short code.

In this scenario, at least during some transitional period, bothtelematics service provider platforms will be supporting service to/fromthe devices in Auto-CO's vehicles. However, hardware constraints preventthe configuring of new short codes on the telematics devices in thevehicles. Hence, there is a need for an intelligent routing solutionthat can route messages to equipment of either of the telematicsentities based on some criteria, such as the identity of thevehicle/device. It is believed that a similar need exists or theintelligent solution may provide advantages in the context of othertypes of application services that utilize mobile messaging service typemessage transport via a wireless/mobile communication network.

SUMMARY

The teachings herein alleviate one or more of the above noted problemswith message routing and provide effective redirection with attendantshort code translations, in the context of an application service thatutilizes mobile messaging service type message transport via a wirelessmobile communication network.

Although other implementations are contemplated, the examples utilize athird party application service type of platform with the common shortcode of the application service assigned to that platform. The thirdparty platform performs the intelligent routing and re-directs allincoming messages, for example, by substitution of appropriate shortcodes selected based on identification the mobile devices. The thirdparty platform, in such an exemplary implementation, effectivelyprovides a point of mediation among the actual application serviceproviders, as a result of message communications/exchange between theservice providers and the third party platform.

An example of the concepts disclosed and discussed in more detail belowmight include a method of processing mobile messaging service messagesrelating to one application service for mobile devices, where the oneapplication service is available from servers of a number of applicationservice providers. Such a method might involve receiving mobilemessaging service messages from mobile devices via a wireless mobilecommunication network. For example, a first message received from afirst mobile device is routed through a wireless mobile communicationnetwork based on a messaging service short code of the one applicationservice, which at least initially was contained in the first message asa destination address. In a similar fashion, another message is receivedfrom a second mobile device, having been routed through the wirelessmobile communication network based on the same messaging service shortcode of the one application service at least initially contained in theas a destination address. However, Processing of the two receivedmessages is somewhat different.

Based on identification of the first mobile device, an address for aserver of a first provider of the one application service is obtainedand used to replace the destination address in the first message as anew destination address for the first message. The first message is thentransmitted or forwarded, for routing based on the address for theserver of the first provider as the new destination address, typicallyto enable delivery thereof to the server of that service provider. Incontrast, based on identification of the second mobile device, anaddress for a server of a second provider of the one application serviceis obtained, which is different from the address for the server of thefirst provider and used to replace the destination address in the secondmessage as a new destination address for the second message. The secondmessage is then transmitted or forwarded, for routing based on theaddress for the server of the second provider as the destinationaddress, typically to enable delivery thereof to the server of thatservice provider. In this way, the messages from two different mobiledevices served by different providers of the one application service,can be routed to the equipment of the different service providers, eventhough the messages from the different mobile devices initially use thesame short code as the initial destination address.

The present concepts are applicable to applications services using avariety of different types of messaging services offered by wirelessmobile communication networks, such as enhanced messaging service (EMS)messages and multi-media messaging service (MMS) messages. Specificexamples discussed in detail below, however, use short messaging service(SMS) type transport for the messages. Also, although the concepts mayapply to other applications services that use such messaging services,for convenience, we will mainly focus on use in a telematics serviceapplication offered to owners of motor vehicles.

Mobile devices may be identified by various information associated withthe devices and/or with the users of the devices. The examples,particularly those using SMS message communications, identify mobiledevices based on their assigned mobile directory numbers.

The server addresses could use any appropriate network addressingscheme. In the examples, the addresses for the servers of the twoapplication service providers are respectively assigned short codes. Insuch a case, the short codes of the providers are different, and thosecodes are different from the short code assigned to the particularapplication service.

As noted, some application services, including some telematics services,may involve messaging service communications from the service providerequipment to the mobile devices. The service provider equipmenttypically includes a source address in each such downstream messagetransmission. It may not be necessary to translate different sourcedestination address, either because they are not critical or because thedifferent servers of the service providers may be able to insert anydesired source address in each such message (e.g. all might insert theone short code of the application service). However, at least in somecases, it may also be desirable to provide address translations onmessages sent from the service provider equipment to the mobile devices.

For this later situation, the methodology discussed herein may offeradditional processing. Such a methodology might further involvereceiving a third mobile messaging service message from the server ofthe first provider addressed to the first mobile device. This messagecontains the address for the server of the first provider as the sourceaddress of the third mobile messaging service message. That sourceaddress is replaced with the messaging service short code of the oneapplication service, and the third message with that short code sourceaddress is sent through the wireless mobile communication network fordelivery to the first mobile device. Another (fourth) mobile messagingservice message is received from the server of the second provideraddressed to the second mobile device, but this message contains theaddress for the server of the second provider as the source address ofthe fourth mobile messaging service message. For the fourth message, thedifferent source address is replaced with the short code of the oneapplication service, and the third message with that short code sourceaddress is sent through the wireless mobile communication network fordelivery to the second mobile device. In this way messages addressed todifferent mobile devices from different servers supporting one commonapplication service arrive at the various mobile devices containing theone short code of the particular application service.

It might be possible to implement various intelligent routing and/oraddress processing functions in support of the messagedirection/distribution among the various service providers, as outlinedabove, at the messaging service centers which store and forward themessages within the wireless mobile communication network. Anotherapproach might be to redirect messages based on intelligent processingin a switch or control node of the network, in a manner analogous toforwarding or redirection of voice calls. However, such solutionsrequire an upgrade of the processing of the message service center orthe switch or other control node, which may require a long time and alarge expense to deploy across a large wireless mobile communicationnetwork. Also, such approaches tend to add processing burdens toexisting elements having other possibly more critical functions.

Hence, the examples described below implement the address translationsand the like in a third party application service provider type ofserver, which is coupled for communication of messaging service messagesvia the wireless mobile communication network. The third partyapplication service provider server is separate from the servers of theproviders that actually offer the application service.

Other concepts discussed herein relate to a server and/or software forimplementing the message processing strategies. A software product orarticle, in accord with this type of concept, includes at least onemachine-readable medium and information carried by the medium. Theinformation carried by the medium may be executable program code(programming instructions), one or more databases and/or otherinformation regarding the handling of the message service messages fromand possibly going to the mobile devices, for the one applicationservice. A server would include an appropriate communication interface,a central processing unit and a memory storing the appropriate programto enable the hardware of the server to implement the message processingstrategy.

Additional advantages and novel features will be set forth in part inthe description which follows, and in part will become apparent to thoseskilled in the art upon examination of the following and theaccompanying drawings or may be learned by production or operation ofthe examples. The advantages of the present teachings may be realizedand attained by practice or use of various aspects of the methodologies,instrumentalities and combinations set forth in the detailed examplesdiscussed below.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 is a high level functional block diagram, useful in explainingmobile stations, network elements and other components that may beinvolved in mobile station communications as well as a telematicsservice that utilizes mobile network resources.

FIG. 2 is a parsed-down version of the diagram of FIG. 1, overlaid withsignal flow arrows, to help illustrate certain processing involved inmobile originated (MO) type SMS message communications, for example,involved in the telematics service.

FIG. 3 also is a parsed-down version of the diagram of FIG. 1, overlaidwith signal flow arrows, but helpful in illustrating certain processinginvolved in mobile terminated (MT) type SMS message communications, forexample, involved in the telematics service.

FIG. 4 is a simplified functional block diagram of a computer that maybe configured as a host or server.

FIG. 5 is a simplified functional block diagram of a personal computeror other work station or terminal device.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent to those skilledin the art that the present teachings may be practiced without suchdetails. In other instances, well known methods, procedures, components,and/or circuitry have been described at a relatively high-level, withoutdetail, in order to avoid unnecessarily obscuring aspects of the presentteachings.

The various examples discussed below relate to message routing andproviding effective redirection with attendant processing of short codetype addresses, in the context of an application service that utilizesmobile messaging service type transport via a wireless mobilecommunication network. The application service utilizes a single shortcode even though the one service is actually supported by multipleservers or the like, typically operated by different service providers.The examples utilize a third party application service type of platformwith the common short code of the application service assigned to thatplatform. The third party platform performs intelligent routing (e.g. byreplacing destination addresses with other short codes or otherdestination server addresses) to re-direct all messages from mobilestations to the servers, for example, based on identification theoriginating mobile devices. The third party platform, in such anexemplary implementation, effectively provides a point of mediationamong equipment of the actual application service providers, via themessage communications/exchange between the service provider equipmentand the third party platform. The platform may also provide short codetranslations of source addresses, during processing of messages directedto mobile stations from the various application servers. To fullyappreciate such operations, it may be helpful to discuss an example of asystem, including various networks, that supports the relevantcommunications and associated short code related processing of themessaging traffic for an exemplary application service.

FIG. 1 is a functional block diagram of an exemplary system of networksfor providing mobile voice telephone services and various data services.In this system, the network 10 is a wireless mobile communicationnetwork.

The network 10 often (but not always) comprises networks operated by anumber of different mobile communication service providers, carriers oroperators, although for simplicity of discussion 10 is assumed to be anetwork operated by one carrier. The communication network 10 providesmobile voice telephone communications as well as other services such astext messaging and various multimedia packet data services, for numerousmobile devices. One type of mobile device shown in the drawing is users'mobile stations 13. The present discussion is applicable to a variety ofapplication services, using mobile network messaging services as thetransport mechanism, where application servers/service providers offerthe same service as identified by a common short code. However, forpurposes of discussion, the drawings show an example in which the commonapplication service relates to a telematics service. Hence, the drawingshows a first vehicle 121 having an associated telematics unit 131configured for crash detection and related emergency communicationfunctions. The drawing also shows a second vehicle 122 having anassociated telematics unit 132 configured for crash detection andrelated emergency communication functions. The telematics units 131, 132are another type of mobile device that communicates via the wirelessmobile communication network 10. The elements indicated by the referencenumeral 10 generally are elements of the carrier's network, although themobile stations 13 typically are sold to the carrier's customers.Similarly, the vehicles and telematics units are sold to customers. Tothe network 10, the telematics units 131, 132 are essentially treated asmobile station devices.

Today, mobile stations such as shown at 13 typically take the formportable handsets, smart-phones or personal digital assistants, datacards for computers, although they may be implemented in other formfactors. The mobile communication network 10 provides communicationsbetween mobile stations 13 as well as communications for the mobilestations with other networks and stations shown generally at 11 outsidethe mobile communication networks.

Hence, the network 10 allows users of the mobile stations 13 that arecurrently operating through the network to initiate and receivetelephone calls with each other as well as through the public switchedtelephone network (PSTN) 19 with telephone stations 21 connectedthereto. The network 10 typically offers a variety of text and otherdata services, including services via the Internet 23, such asdownloads, web browsing, e-mail, etc. via servers shown generally at 25as well as message communications with terminal devices representedgenerally by the personal computer (PC) 27. A number of the dataservices provide messaging services. Examples of such services includeSMS, EMS and MMS. Although the present teachings may be applied to anyof these or other types of messaging services, for purposes of aspecific example to discuss here, we will assume that the network 10allows SMS type text messaging between mobile stations 13 and similarmessaging with other devices, e.g. via the Internet 23.

Although other elements are included for vehicle monitoring, crashdetection and user interface, the communication elements and locationelements of each telematics unit 131, 132 are generally similar tocorresponding elements of a regular mobile station 13. To the wirelessmobile communication network 10, each telematics unit 131, 132 isprovisioned and operates in a manner generally similar to a mobilestation (MS) 13, although the network services available to thetelematics units may be somewhat limited in comparison to thoseavailable to various mobile stations 13. For example, the telematicsunits 131, 132 may be provisioned only to send/receive voice and SMStype messaging communications to/from call center(s) of the telematicsservice provider(s).

The network 10 may implement wireless communications with the mobilestations 13 (and similar mobile telematics units 131, 132) via any of avariety of different standard communication technologies common inpublic wireless mobile communication networks. Examples of suchtechnologies include various CDMA standards, including 3GPP2 variantsthereof (e.g. 1XRTT or EVDO), as well as TDMA and GSM standardsincluding 3GPP variants (e.g. LTE or UMTS). The mobile stations 13 andthe communications elements of the telematics units 131, 132 would beconfigured to communicate in accord with the wireless standard supportedby the network 10, although many such mobile devices have the capabilityof communicating via a number of networks that may utilize differentstandardized technologies (multi-mode devices).

The mobile communication network 10 typically is implemented by a numberof interconnected networks. Hence, the overall network 10 may include anumber of radio access networks (RANs), as well as regional groundnetworks interconnecting a number of RANs and a wide area network (WAN)interconnecting the regional ground networks to core network elements,such as SMS messaging centers (SMSCs) 29 and/or multimedia messagingcenters (MMSCs—not shown). A regional portion of the network 10, such asthat serving mobile stations 13 and the telematics units 131, 132, willtypically include one or more RANs and a regional circuit and/or packetswitched network and associated signaling network facilities.

Physical elements of a RAN operated by one of the mobile serviceproviders or carriers, include a number of base stations represented inthe example by the base stations 17. Although not separately shown, sucha base station (BS) 17 typically comprises a base transceiver system(BTS) which communicates via an antenna system at the site of the basestation and over the airlink with one or more of the mobile devices 13,131, 132, when the mobile devices are within range. Each base station(BS) 17 typically includes a BTS coupled to several antennas mounted ona radio tower within a coverage area often referred to as a “cell.” TheBTS is the part of the radio network that sends and receives RF signalsto/from the mobile devices that the base station currently serves.

The radio access networks also include or connect to a traffic networkrepresented generally by the cloud shown at 15, which carries the usercommunications for the mobile stations 13 and the telematics units 131,132 between the base stations 17 and other elements with or throughwhich the various wireless mobile devices communicate. Individualelements such as switches and/or routers forming the traffic network 15are omitted here for simplicity.

A Mobile Directory Number (MDN) is the telephone number assigned to amobile station, which a calling party or device inputs in order to callor send a message to the particular mobile station. To call a mobilestation 13, for example, a user of a PSTN telephone or of another mobilestation dials the MDN associated with the particular mobile station 13.To send a MMS message or a SMS message to destination mobile station 13,as another example, typically entails input of the MDN of that mobilestation. A Mobile Identification Number (MIN) is an identificationnumber used by the network 10 to signal a particular mobile station. TheMIN is formatted like a telephone number, and the MIN may be the same asthe MDN. However, increasingly, the network 10 assigns a differentnumber for use as the MIN and translates the MDN input by a calling orother originating party into the MIN that the network 10 uses toestablish the call or send the message to the destination mobilestation. Of these numbers assigned to the mobile station, the MDNtypically is the number or address of the station known and used byother parties or stations. To facilitate communications through thenetwork 10, the telematics units 131, 132 also are assigned MDN and MINnumbers, in essentially the same manner as are the mobile stations 13.

The traffic network portion 15 of the mobile communication network 10connects to the public switched telephone network (PSTN) 19. This allowsthe network 10 to provide voice grade call connections between mobilestations and regular telephones connected to the PSTN 19. The drawingshows one such telephone at 21. This interconnection supports regularvoice telephone traffic of the mobile stations 13 as well as voicecommunications for the telematics units 131, 132, for example, withtelephone equipment (not shown) at one or more call centers of thecompanies providing the telematics type application service.

The traffic network portion 15 of the mobile communication network 10connects to a public packet switched data communication network, such asthe network commonly referred to as the “Internet” shown at 23. As notedearlier, packet switched communications via the traffic network 15 andthe Internet 23 may support a variety of user services through thenetwork 10, such as mobile station communications of text and multimediamessages, e-mail, web surfing or browsing, programming and mediadownloading, etc. For example, the mobile stations 13 may be able toreceive messages from and send messages to user terminal devices, suchas personal computers, either directly (peer-to-peer) or via variousservers. The drawing shows one such user terminal device as a personalcomputer (PC) at 27 and one sever 25, by way of example.

For purposes of the discussion of handling of messaging traffic, bymanipulations based on short codes, we will concentrate on an SMS typeimplementation of the messaging service that carries or transports thedata portion of the application service communications through thenetwork 10. Those skilled in the art will recognize, however, that thetelematics application service or other types of application servicesmay utilize other types of the messaging services available in thetypical wireless mobile communication network 10, and that the presentconcepts are equally applicable to application services using thoseother types of messaging services through the network.

Wireless carriers developed the short message service (SMS) to transmittext messages for display on the mobile stations. In many existingnetwork architectures, the SMS traffic uses the signaling portion of thenetwork 15 to carry message traffic between a Short Message ServiceCenter (SMSC) 29 and the mobile stations 13. The SMSC 29 supports mobilestation to mobile station delivery of text messages. However, the SMSC29 also supports communication of messages between the mobile stationsand devices coupled to other networks. For example, the SMSC 29 mayreceive incoming IP message packets from the Internet 23 for deliveryvia the network 15, one of the base stations 17 and a signaling channelover the air link to a destination mobile station 13. For this latertype of SMS related communications, the network 10 also includes one ormore Short Message Peer-to-Peer (SMPP) protocol gateways 31. The SMPPgateway 31 provides protocol conversions, between SMPP as used by theSMSC 29 and the protocols used on the Internet 23 or other IP network33. SMPP messages ride on IP transport, e.g. between the gateway 31 andthe SMSC 29.

The exemplary system also includes one or more other packetcommunication networks 33 connected to the mobile network 10. Thenetwork 33 may be a private packet data network operated by the samecarrier that operates network 10 for its own purposes, or the network 33may be a secure network interconnected among several parties workingtogether to provide certain secure services. Alternatively, the network33 may be the Internet 23. Of note for purposes of the presentdiscussion, the network 33 provides packet data communications betweenthe gateway (GW) 31 to the traffic network 15, for a number ofapplication servers.

As noted earlier, in the discussion regarding the various mobiledevices, the present discussion is applicable to a variety ofapplication services, using mobile network messaging services as thetransport mechanism, where application servers/service providers offerthe same service as identified by a common short code. However, forpurposes of discussion, the drawings show an example in which the commonapplication service relates to a telematics service offered to owners ofvehicles 121, 122. Hence, the servers 35 and 37 are application serversoperated by entities that provide the telematics service.

The owners of the vehicles 121 and 122 subscribe to the telematicsservice offered by the vehicle manufacturer, called Auto-CO in ourexample. For various reasons, however, the actual service is provided bytwo different service provider companies, CO-A and CO-B, typically undercontract with Auto-CO. Service for the first vehicle 121 is allocated toCO-A, whereas service for the second vehicle 122 has been allocated toCO-B. Each service provider will operate a call center, which supportscertain data communications as well as voice communications with theprovider's call attendant personnel. In a typical operation, atelematics unit will detect a vehicle condition indicating a crash orother emergency condition of the vehicle or will detect actuation of an“emergency” or “panic” button associated with the telematics unit by anoccupant of the vehicle. In response, the telematics unit initiates acommunications through the mobile wireless communication network 10 withthe appropriate provider's call center. Certain data regarding thevehicle and the event are communicated to the call center's dataequipment, via SMS in the present example. The communication alsoresults in a voice call between the center and the telematics unit inthe vehicle. Similar procedures may be used in non-emergencycommunications of the telematics unit, e.g. for turn-by-turn directionsor location based concierge service.

The present discussion of message handling focuses on the messageprocessing, that is to say the processing of the SMS messages in thetelematics example. Hence, voice call elements related to the telematicsservice are omitted here for convenience. As shown in the drawings, eachtelematics service provider will operate at least one applicationserver. Those skilled in the art will recognize that conventional callforwarding or redirection techniques can be used to distribute the voicecalls from the telematics units to voice equipment at each respectiveservice provider's call center.

In our example, the first service provider CO-A operates the telematicsapplication server 35, whereas the second service provider CO-B operatesthe telematics application server 37. Each of these servers receivesmessages and provides appropriate communications of the messages toterminals of the provider's personnel at the respective call center (notseparately shown). In response to inputs at the terminals, each server35 or 37 also can send SMS messages back through the network 10 to themobile devices/telematics units in the vehicles the provider services.

Hence, two of the application servers 35 and 37, in this example, offerthe same application service, such as the data component of theexemplary vehicle telematics service for customers of Auto-CO. In theexample, the servers may be operated by two different providers of thatone service. Of course, there may be additional providers operatingother servers. Also, for discussion purposes, we will assume eachservice provider CO-A, CO-B operates one server, although in an actualimplementation either one or both service providers may operate two ormore servers and a known mechanism to distribute the traffic andprocessing load amongst the respective provider's servers.

The application server 39 replaces the address in various messages withshort codes of the respective servers, as part of a short code basedmessage exchange between that server 39 and other application serverssuch as 35 and 37. In the mobile originated (MO) message processing, theserver 39 replaces the initial common destination address with the shortcode of the server of the provider that services the particular sendingdevice. In this way, the server 39 supports the distribution of SMSmessaging traffic among the different application servers that providethe one service, that is to say among the application servers 35 and 37that provide the data component of the telematics service, in thisexample. In mobile terminated message processing, the server 39 may alsotranslate an address of the sending server 35 or 37 into the one shortcode for the telematics application service, as a source address foreach message sent to a telematics type mobile device.

The server 39 is operated by a ‘third party’ in that it is operated by aparty other than those operating the servers 35 and 37, to provideneutrality in the mediation of traffic amongst the servers 35 and 37.The third party operating the server 39 could be the carrier operatingthe network 10, in which case, the server 39 could be implemented as anintegral part of the network 10, or the third party operating the server39 could be independent of the network operator/carrier as well.

In the example, we will assume that the third party server 39 providesthe short code manipulations and thereby facilitates the messageexchange, for the one application service, that is to say for thetelematics service of the vehicle manufacturer Auto-CO. Those skilled inthe art will recognize that the server 39 or other similar servers mayoffer similar messaging traffic processing services with respect toother application services.

Examples of mobile messaging service messages typically provided by awireless mobile communication networks such as network 10 in theillustration today include short messaging service (SMS) messages,enhanced messaging service (EMS) messages and multi-media messagingservice (MMS) messages. EMS is an application-level extension to ShortMessage Service (SMS) for cellular phones available on GSM, TDMA andCDMA networks. MMS adds capabilities for transport of a wider range ofcontent in the messages. For purposes our telematics example, we haveassumed that the messages used are SMS type messages, although thepresent concepts encompasses MMS, EMS and other messaging servicecommunications through the wireless mobile communication network 10.Hence, although other configurations may be used, in this example, theapplication servers 35, 37 and 39 are ESME servers configured toimplement application services that utilize SMS type message transportthrough the wireless mobile communication network 10.

An SMS message includes source and destination address fields. Formessages from a mobile device, the source address is the MDN of thesending customer's mobile station or telematics unit. The destinationaddress may be a MDN of a destination station or some other form ofrecognizable address. Of note for purposes of this discussion, one typeof alternative address is a short code, typically four, five, six,eight, or twelve digits.

A server hosting an ESME application may be assigned a short code.Hence, the network 15 routes outgoing messages from a mobile station 13or from a telematics unit 131 or 132 using a short code for thedestination address of the appropriate ESME application. A short codefor SMS is a digit string that is not a telephone number which istypically 7 digits or 10 digits. For example, a short code can be a4-digit, a 5-digit, a 6-digit, an 8-digit string or a 12-digit string.

The SMSC 29 communicates with external customer equipment, typicallycomputers hosting the ESME applications such as those on servers 35, 37and 39, via an IP network, in this case the network 33. To provide theinterface for such communications, the network 17 includes the SMPPgateway (GW) server 31. The SMPP gateway 31 communicates with the SMSC29 via an internal IP link or network (not separately shown), and thegateway 31 communicates with the packet data network 33 (and/or thepublic Internet 23). The gateway 31 allows the SMSC 29 to receive andsend messages in IP packet format. The SMPP gateway 31 is the entitywithin the wireless mobile communication network 10 that acts as anintermediary between the wireless service provider network 10 and theexternal application server community. For example, the gateway server31 converts messages in protocol(s) used by the ESME applications onethe servers 35, 37 and 39, e.g. Extensible Markup Language (XML),Hypertext Mail Protocol (HTMP), etc., to and from the SMPP protocol usedfor SMS services through the network 10. The SMPP messages ride on IPtransport, e.g. between the gateway 31 and the SMSC 29.

As noted, each SMS message includes source and destination addressfields. Typically, each address is either an MDN of a mobile station ora short code of an application service. The network routes a SMS messagewith a MDN destination address all the way through to the addressedmobile station 13 (or similarly to a telematics units 131 or 132). Thenetwork routes a SMS message with a short code destination address to aservice provider application corresponding to the short code. Dependingon the service, the application may process the message, e.g. to countvotes; or the network may translate the short code to a destinationaddress, e.g. an IP address of an external customer's server, such asthe ESME server of a value added service provider or the like.

SMS routing thus allows use of short codes as a mechanism to routemessages to/from an application service provider, as opposed tocommunication of messages between end user devices. For this purpose,the short code is recognized by a control application as being a messageto a service provider as opposed to a message between SMS user devices,and the control application translates the short code to direct themessage to the appropriate service provider platform.

For an outgoing SMS message from a mobile station 13, the messageincludes a source address comprising a field for the normal telephonenumber of the originating device and a field for another deviceidentifier assigned by the network operator. In a typical SMScommunication from a mobile station 13, the telephone number is the MDNwhereas the other identifier is a MIN or IMSI. Similar identifiers canbe used for messages from one of the telematics units 131, 132.

For SMS messages originating at a mobile station 13 or telematics unit,a node of the traffic network 15 such as a mobile switching centerdetermines where to route the message. For a mobile originated (MO)message containing a telephone number of a destination (e.g. an MDN ofanother mobile station), the control node typically routes the messageto one of several SMSCs 29 deployed in the network 15, based on the MINof the sending device. Essentially, the control node looks up the pointcode or other form of address for the appropriate SMSC 29 based on theMIN of the sending mobile station 13 contained in the source field ofthe received SMS message. The SMSC 29 then determines how to deliver themessage based on the destination address of the message, e.g. adirectory number of another mobile station.

Short code routing could utilize a similar procedure to route messagesto an SMSC, which determines proper handling. However, as such messagestypically are directed to another server (of the application serviceprovider), the network 15 can be configured to bypass the SMSC 29 forsome or all mobile originated traffic. Hence, in the illustratedexamples, the mobile switching center or other control node of thenetwork 15, upon receiving a SMS message from a mobile station 13 or atelematics unit 131 or 132, which contains a short code as thedestination address, routes the message through the network 15 to anappropriate one of the SMPP gateways 31. For traffic/load managementreasons, a particular gateway 31 may be provisioned to handle therelevant traffic, e.g. for all mobile originated traffic addressed toany/all short codes or for mobile originated traffic addressed to aparticular short code or set of short codes. For example, a SMPP gateway31 designated for ‘voting’ type SMS application traffic may also handlemobile originated short code traffic for other applications or may bedesignated just to further handle upstream telematics transmissions. Ofnote for purposes of this discussion of handling of messaging trafficusing a short code for one application, such as the telematics service,the network 10 routes all upstream messages that contain the one shortcode (the telematics service short code) through the traffic network 15to a SMPP gateway 31, while bypassing the SMSC 29.

The gateway 31 normally routes SMS messages addressed short codes to anapplication server to which the particular short code has been assigned.For the telematics service, the telematics short code is assigned to thethird party application server 39, therefore the SMPP gateway 31 routesthe telematics SMS message to the application server 39, via the network33 in our example. Such routing may entail translation of the one shortcode to an IP address of the server 39 (possibly with a port ID for thetelematics service).

Upon receiving each mobile messaging service message, SMS message in theexample, from a mobile device (mobile station 13, or telematics unit 131or 132), via the wireless mobile communication network 10, the server 39uses the source identification (MDN and/or MIN) to generate adestination address of the server 35 or 37 serving the sending device.The server 39 could generate an IP address and deliver the messagedirectly through the network 33 to the appropriate server 35 or 37.However, in the example, the server 39 replaces the destination addressof the message with a new short code uniquely assigned to the equipmentof the particular service provider that offers telematics service to thesending customer/device. Obtaining the new short code, for example,could utilize a look-up table based on the complete MDN or based on aportion of the MDN (corresponding to a range of customer devices) toidentify the short code of the appropriate server. After addressreplacement with the short code as a new destination address, the thirdparty application server 39 then forwards the message with the shortcode back to the SMPP gateway 31 for normal processing and deliverythrough the network 33 to the appropriate server 35 or 37. A moredetailed example of the processing of a mobile originated telematicsmessage communication is discussed below with regard to FIG. 2.

As discussed above, the destination address of a SMS message usuallycontains a directory number or other full address of the destination, orthe destination address field contains a predefined short code. In anormal operation for a SMS transmission to a mobile station 13, an SMSC29 receives the message containing the MDN of the destination station 13and queries the particular home location register that stores the recordassociated with that station's MDN for information about the mobilestation 13 that is needed to route the message to the mobile station atits current location. The home location register responds by providingthe current routing information, and the SMSC 29 uses that informationto send the message through the network 15 and the serving base station17 for delivery to the destination mobile station 13.

Messages sent from the application service providers' equipment to thetelematics unit type mobile devices 131, 132 (mobile terminated or “MT”type traffic) are handled in much the same way. However, it may bedesirable to have the telematics short code as the source address insuch downstream messages when delivered to those mobile devices. Anexample using a short code translation by the third party applicationserver 39 is discussed below with regard to FIG. 3. However, the thirdparty server solution may not be necessary for the MT call flow if theoriginating address can be set to any value at application servers ofthe providers, such as servers 35 and 37.

It might be possible to implement various intelligent routing and/ortranslation functions in support of the message direction/distributionamong the various service providers at the messaging service centerssuch as the SMSCs 29 in the example of FIG. 1. Another approach might beto redirect messages based on intelligent processing in a switch orcontrol node of the network 15, in a manner analogous to forwarding orredirection of voice calls. However, such solutions require an upgradeof the processing of the message service center or the switch or controlnode, which may require a long time and a large expense to deploy acrossa large wireless mobile communication network 10. Also, such approachestend to add processing burdens to existing elements that may have otherpossibly more critical functions. Hence, the examples implement theaddress and short code processing for mobile originated messages andpossibly the translations for mobile terminated messages, for thetelematics application service in our example, in another applicationserver represented by the server 39 in the diagrams.

Also, the communications to/from the application server 39 could beinitiated by any of several different elements of the network 10. Forexample, an SMSC could receive the relevant messages and send them tothe server 39 for the necessary short code processing functions.However, the short code routing directly to a gateway 31 bypasses theSMSC and reduces processing burdens on the SMSC. By pointing aparticular short code to a selected one of the gateways that isotherwise under utilized, it may also be possible to balance messagetraffic loading among various SMPP gateways that handle SMS in-bound andout-bound related traffic for a number of different applicationservices.

It may be helpful now to discuss some examples of actual messageprocessing, in the context of the exemplary telematics service. First,we will consider processing of mobile originated (MO) messages, in thiscase originated from the mobile devices that form or are incorporated inthe exemplary telematics units, with reference to FIG. 2. For purposesof the example, we will assume that telematics units 131, 132 areprogrammed or hard coded with the short code “11111” assigned to thetelematics service offered by Auto-CO to purchasers of its vehicles 121,122. As shown by the arrows, in step 1, the units 131, 132 at varioustimes send their upstream messages through the respective serving basestations 17 to the traffic network 15, for example, in response tocrashes, user activation of a panic button or other triggeringevent/input. Each such message includes the short code 11111 in thedestination address field of the message. However, the message from theunit 131 includes the MDN and/or MIN of the telematics unit 131 in thesource field(s), and the message from the unit 132 includes the MDNand/or MIN of the telematics unit 132 in the source field(s). Thetraffic network 15 routes all such message that carry the short code11111 in the destination address field to one of the SMPP gateways 31,as shown by the arrow representing step 2.

Programming or provisioning data in the SMPP gateway 31 causes thatgateway to recognize that the telematics short code 11111 is assigned tothe third party application server 39. Hence, the SMPP gateway 31 sendsall messages with that code as the destination address through thenetwork 33 to the third party application server 39, as shown by thearrow representing step, for example, by using an IP address of thatserver 39 as provisioned in the gateway 31 with respect to the 33333short code.

The processing at the server 39 distinguishes between different sourcesfor the upstream (MO) SMS messages. Messages from mobile devices ofvehicle owners serviced by provider CO-A are to be directed to server35, whereas messages from mobile devices of vehicle owners serviced byprovider CO-B are to be directed to server 37. Hence, for discussionpurposes, we will assume that the service for vehicle 121 is assigned toprovider CO-A, therefore messages from the telematics unit 131 are to bedirected to server 35. In contrast, in our example, we will assume thatthe service for vehicle 122 s assigned to provider CO-B, thereforemessages from the telematics unit 132 are to be directed to server 37.

In our example, the addresses of the application servers 35 and 37 alsoare short codes. The application server 35 of service provider CO-A isassigned short code 22222, whereas the application server 37 of serviceprovider CO-B is assigned short code 33333.

As outlined above relative to steps 1 and 2, the third party platform 39receives all MO messages for short code 11111, for the telematicsservice of Auto-CO vehicles. Based on identification of each mobiledevice, the server 39 identifies an address for a server of a theappropriate provider of that application service; and the server 39replaces the destination address of the message as received at theserver 39 with the address of that application server, to enableforwarding of the MO short coded message through the network 33 to thethird party application server 39. The new destination address could bean IP address for routing of the message directly through the network 33to the appropriate server 35 or 37, but in our example, the newdestination address is another short code assigned to the appropriateapplication server 35 or 37.

In the example, at step 3, the server 39 checks the originating addressof the sending device (e.g. MDN and/or MIN) and based on that addressgenerates an address of one of the servers 35 and 37. For example, for afirst message received from the telematics unit 131 (first device inthis example) of vehicle 121 (serviced by CO-A), the server 39 obtainsfrom a look-up table or the like the short code 22222 for theapplication server 35. Then, the third party application server 39replaces the destination address in the received message with the shortcode address 22222 for the server 35 of the first telematics serviceprovider CO-A, as the new destination address in the first message thatcame from the telematics unit 131. The third party application server 39sends the message back to the SMPP gateway 31. In step 4, for the firstmessage, the SMPP gateway 31 in turn forwards the message based on theshort code 22222 through the network 33 to the application server 35 forthe first telematics service provider CO-A, for example, by using an IPaddress of that server 35 as provisioned in the gateway 31 with respectto the 22222 short code.

In contrast, with respect to the second message that comes to the server39 from the telematics unit 132, at step 3, the server 39 checks theoriginating address of the sending device (e.g. MDN and/or MIN) andbased on that address obtains from a look-up table or the like the shortcode 33333 for application server 37. Then, the third party applicationserver 39 replaces the destination address in the received message withthe short code address 33333 for the server 37 of the second telematicsservice provider CO-B, as the new destination address in the secondmessage that came from the telematics unit 132. The third partyapplication server 39 sends the message back to the SMPP gateway 31. Instep 4, for the second message, the gateway 31 in turn forwards themessage based on the short code 33333 through the network 33 to theapplication server 37 for the second telematics service provider CO-B,for example, by using an IP address of that server 37 as provisioned inthe gateway 31 with respect to the 33333 short code.

As shown by the example of two messages processed through the flow ofFIG. 2, the application server 39 redirects messages initially addressedto the one common short code for the telematics service to equipment 35and 37 of two different providers, based on identification of therespective mobile devices. In this way, the messages from two differentmobile devices served by different providers of the one applicationservice, can be routed to the equipment of the different serviceproviders, even though the messages from the different mobile devicesinitially use the same short code as the initial destination address.

As noted, some application services, including some telematics services,may involve messaging service communications from the service providerequipment to the mobile devices (mobile terminated or “MT” typetraffic). The service provider equipment typically includes a sourceaddress in each such downstream message transmission. It may bedesirable to have the telematics short code, e.g. 11111, as the sourceaddress in such downstream messages when they arrive at mobile devicessuch as telematics units 131, 132. It may be possible to that theservers 35 and 37 set the source address to this short code value, inall downstream message transmissions. Alternatively, the third partyapplication server 39 could offer a short code translation of the sourceaddress. FIG. 3 illustrates a call flow as might utilize such a featureor service on the third party application server 39.

As shown in FIG. 1, step 5 involves downstream message transmissions,initially sent from the application servers 35 and 37 of the twotelematics service providers to the units 131, 132 of their respectivecustomers. In step 5, each server sends the respective message throughthe network 33 with the appropriate destination MDN through the network33 to the SMPP gateway 31. Here, we assume that the servers 35 and 37have not set the source address to the 11111 short code of the of thetelematics service. Hence, the message from server 35 for telematicsunit 131 carries the short code 22222 of the server 35, and the messagefrom server 37 for telematics unit 132 carries the short code 33333 ofthe server 37. In the normal manner, these messages addressed to mobiledevice destinations are routed through packet data network 33 to one ofthe SMPP gateways 31. The SMPP gateway 31 forwards these messages to thethird party application server 39, through the network 33 in our example(for ease of illustration, the arrows 5 go from the servers 35, 37 tothe server 39).

Upon receipt of the message from server 35 for telematics unit 131, thethird party application server 39 translates the short code 22222 of theserver 35 into the 11111 short code of the of the telematics service,and replaces the short code 22222 with the short code 11111 in thesource address field of the message. Similarly, upon receipt of themessage from server 37 for telematics unit 132, the third partyapplication server 39 translates the short code 33333 of the server 37into the 11111 short code of the of the telematics service, and replacesthe short code 33333 with the short code 11111 in the source addressfield of that message.

In step 6 (FIG. 3), each message with the translated source address, isforwarded through the packet data network 33 to the SMPP gateway 31.These messages still contain the MDNs of the respective telematics units131, 132. Hence, in the normal manner, the gateway 31 forwards thesemessages through the mobile traffic network 15, at step 7. This wouldtypically involve routing to an SMSC (shown in FIG. 1 but not in FIG.3), and the network 10 would subsequently deliver the messages to therespective telematics units 131, 132 as shown as arrows at step 8. Tothe receiving telematics units 131, 132, the messages would appear tohave come from the same source corresponding to the one short codeassigned for the telematics service of Auto-CO.

As shown by the above discussion, functions relating to the processingof short codes/addresses and redirecting messages for one applicationservice as among equipment of multiple providers of the one service maybe implemented on one or more computers connected for data communicationvia the components of a packet data network, and thus with the wirelessmobile communication network, which operate as the third partyapplication server 39 as shown in FIGS. 1 to 3. Although special purposedevices may be used, such devices also may be implemented using one ormore hardware platforms intended to represent a general class of dataprocessing device commonly used to run “server” programming, for exampleESME server programming, so as to implement the functions discussedabove, albeit with an appropriate network connection for datacommunication.

As known in the data processing and communications arts, ageneral-purpose computer typically comprises a central processor orother processing device, an internal communication bus, various types ofmemory or storage media (RAM, ROM, EEPROM, cache memory, disk drivesetc.) for code and data storage, and one or more network interface cardsor ports for communication purposes. The software functionalitiesinvolve programming, including executable code as well as associatedstored data, e.g. files used for the short code related functionsdescribed in the examples above. The software code is executable by thegeneral-purpose computer that functions as the third party applicationserver or the like that performs the address processing functions. Inoperation, the code is stored within the general-purpose computerplatform. At other times, however, the software may be stored at otherlocations and/or transported for loading into the appropriategeneral-purpose computer system. Execution of such code by a processoror other CPU implementation in the computer platform enables theplatform to implement the methodology for message processing in supportof the application service offered by multiple provider platforms, inessentially the manner performed in the implementations discussed andillustrated herein.

FIGS. 4 and 5 provide functional block diagram illustrations of generalpurpose computer hardware platforms. FIG. 4 illustrates a network orhost computer platform, as may typically be used to implement a server.FIG. 5 depicts a computer with user interface elements, as may be usedto implement a personal computer (PC) or other type of work station orterminal device, although the computer of FIG. 5 may also act as aserver if appropriately programmed. It is believed that those skilled inthe art are familiar with the structure, programming and generaloperation of such computer equipment and as a result the drawings shouldbe self-explanatory.

The hardware for a server platform or computer, for example, includes adata communication interface for packet data communication. The serverhardware also includes a central processing unit (CPU), in the form ofone or more processors, for executing program instructions. The serverplatform typically includes an internal communication bus, programstorage and data storage for various data files to be processed and/orcommunicated by the server, although the server often receivesprogramming and data via network communications. The hardware elements,operating systems and programming languages of such servers areconventional in nature, and it is presumed that those skilled in the artare adequately familiar therewith. Of course, the functions of variousservers, such as each of the application servers 35, 37 and 39 discussedabove, may be implemented in a distributed fashion on a number ofsimilar hardware platforms, to distribute the processing load.

Hence, aspects of the methods of short code based message redirectionand/or translation functions outlined above may be embodied inprogramming. Program aspects of the technology may be thought of as“products” or “articles of manufacture” typically in the form ofexecutable code and/or associated data that is carried on or embodied ina type of machine readable medium. “Storage” type media include any orall of the memory of the computers, processors or the like, orassociated modules thereof, such as various semiconductor memories, tapedrives, disk drives and the like, which may provide storage at any timefor the software programming. All or portions of the software may attimes be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of an operator intothe computer platform of the third party application server. Thus,another type of media that may bear the software elements includesoptical, electrical and electromagnetic waves, such as used acrossphysical interfaces between local devices, through wired and opticallandline networks and over various air-links. The physical elements thatcarry such waves, such as wired or wireless links, optical links or thelike, also may be considered as media bearing the software. As usedherein, unless restricted to tangible “storage” media, terms such ascomputer or machine “readable medium” refer to any medium thatparticipates in providing instructions to a processor for execution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement the addressand short code processing regarding messages for the one applicationservice, as described herein. Volatile storage media include dynamicmemory, such as main memory of such a computer platform. Tangibletransmission media include coaxial cables; copper wire and fiber optics,including the wires that comprise a bus within a computer system.Carrier-wave transmission media can take the form of electric orelectromagnetic signals, or acoustic or light waves such as thosegenerated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer can read programming code and/ordata. Many of these forms of computer readable media may be involved incarrying one or more sequences of one or more instructions to aprocessor for execution.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

APPENDIX: ACRONYM LIST

The description above has used a large number of acronyms to refer tovarious services, messages and system components. Although generallyknown, use of several of these acronyms is not strictly standardized inthe art. For the convenience of the reader, the following listcorrelates acronyms to terms, as used in the detailed description above.

1XRTT—One (1) times (×) Radio Transmission Technology

3GPP—3rd Generation Partnership Project

3GPP2—3rd Generation Partnership Project 2

BS—Base Station

BTS—Base Transceiver System

CD—Compact Disk

CD-ROM—Compact Disk-Read Only Memory

DVD—Digital Video Disk

DVD-ROM—Digital Video Disk-Read Only Memory

EEPROM—Electrically Erasable Programmable Read Only Memory

EPROM—Erasable Programmable Read Only Memory

ESME—External Short Message Entity

EVDO—1x/Evolution—Data Only

GSM—Global System for Mobile

GW—Gateway

HTMP—Hypertext Mail Protocol

HTTP—Hypertext Transfer Protocol

ID—IDentification

IP—Internet Protocol

IR—InfraRed

LTE—Long Term Evolution

MDN—Mobile Director Number

MIN—Mobile Identification Number

MMS—Multimedia Messaging Service

MMSC—Multimedia Messaging Service Center

MO—Mobile Originated

MS—Mobile Station

MT—Mobile Terminated

PROM—Programmable Read Only Memory

RAM—Random Access Memory

RAN—Radio Access Network

RF—Radio Frequency

ROM—Read Only Memory

SMPP—Short Message Peer-to-Peer

SMS—Short Messaging Service

SMSC—Short Messaging Service Center

UMTS—Universal Mobile Telecommunications Systems

XML—Extensible Markup Language

1. A method of processing mobile messaging service messages relating toone application service for a plurality of mobile devices where the oneapplication service is available from servers of a plurality ofapplication service providers, the method comprising steps of: receivinga first mobile messaging service message from a first mobile devicerouted through a wireless mobile communication network based on a firstmessaging service short code of the one application service at leastinitially contained in the first message as a destination address; basedon identification of the first mobile device, obtaining a secondmessaging service short code for a server of a first provider of the oneapplication service; replacing the first messaging service short code inthe first message with the second messaging service short code for theserver of the first provider as a new destination address for the firstmessage; forwarding the first message for routing based on the secondmessaging service short code for the server of the first provider as thenew destination address of the first message; receiving a second mobilemessaging service message from a second mobile device routed through thewireless mobile communication network based on the first messagingservice short code of the one application service at least initiallycontained in the second message as a destination address; based onidentification of the second mobile device, obtaining a third messagingservice short code for a server of a second provider of the oneapplication service, different from the second messaging service shortcode for the server of the first provider; replacing the first messagingservice short code in the second message with the third messagingservice short code for the server of the second provider as a newdestination address for the second message; and forwarding the secondmessage for routing based on the third messaging service short code forthe server of the second provider as the new destination address of thesecond message.
 2. The method of claim 1, wherein: identification of thefirst mobile device comprises a mobile directory number assigned to thefirst mobile device contained in the received first mobile messagingservice message; and identification of the second mobile devicecomprises a mobile directory number assigned to the second mobile devicecontained in the received second mobile messaging service message. 3.The method of claim 1, wherein the first and second mobile messagingservice messages are short messaging service (SMS) messages.
 4. Themethod of claim 3, wherein: the application service is a vehiculartelematics service; and the first and second mobile devices aretelematics units mounted in first and second vehicles.
 5. The method ofclaim 1, wherein the first messaging service short code assigned to theone application service, the second messaging service short codeassigned to the first provider, and the third messaging service shortcode assigned to the second provider are different from each other. 6.The method of claim 1, further comprising: receiving a third mobilemessaging service message from the server of the first provideraddressed to the first mobile device, the third message containing thesecond messaging service short code for the server of the first provideras the source address of the third mobile messaging service message;replacing the second messaging service short code for the server of thefirst provider with the first messaging service short code of the oneapplication service, as the source address of the third mobile messagingservice message; forwarding the third message for routing through thewireless mobile communication network to the first mobile device;receiving a fourth mobile messaging service message from the server ofthe second provider addressed to the second mobile device, the fourthmessage containing the third messaging service short code for the serverof the second provider as the source address of the fourth mobilemessaging service message; replacing the third messaging service shortcode for the server of the second provider with the first messagingservice short code of the one application service, as the source addressof the fourth mobile messaging service message; and forwarding thefourth message for routing through the wireless mobile communicationnetwork to the first mobile device.
 7. The method of claim 1, wherein:the steps are implemented in a third party application service providerserver coupled for communication of messaging service messages via thewireless mobile communication network; and the third party applicationservice provider server is separate from the server of the firstprovider of the one application service and from the server of thesecond provider of the one application service.
 8. An applicationserver, comprising: an interface for message communication with awireless mobile communication network; a central processing unit; amemory; a program stored in the memory for execution by the centralprocessing unit, wherein execution of the program configures the centralprocessing unit to operate the application server to perform functions,including functions to: a) receive a first mobile messaging servicemessage from a first mobile device routed through a wireless mobilecommunication network based on a first messaging service short code ofthe application service at least initially contained in the firstmessage as a destination address; b) based on identification of thefirst mobile device, obtain a second messaging service short code for aserver of a first provider of the one application service; c) replacethe first messaging service short code in the first message with thesecond messaging service short code for the server of the first provideras a new destination address for the first message; d) forward the firstmessage for routing based on the second messaging service short code forthe server of the first provider as the new destination address of thefirst message; e) receive a second mobile messaging service message froma second mobile device routed through the wireless mobile communicationnetwork based on the first messaging service short code of the oneapplication service at least initially contained in the second messageas a destination address; f) based on identification of the secondmobile device, obtain a third messaging service short code for a serverof a second provider of the one application service, different from thesecond messaging service short code for the server of the firstprovider; g) replace the first messaging service short code in thesecond message with the third messaging service short code for theserver of the second provider as a new destination address for thesecond message; and h) forward the second message for routing based onthe third messaging service short code for the server of the secondprovider as the new destination address of the second message.
 9. Theapplication server of claim 8, wherein the program configures theapplication server as an external short message entity (ESME) server.10. The application server of claim 9, wherein the program enables theapplication server to process short message service (SMS) type messagesas the first and second messages.
 11. The application server of claim10, wherein: identification of the first mobile device comprises amobile directory number assigned to the first mobile device contained inthe received first mobile messaging service message; and identificationof the second mobile device comprises a mobile directory number assignedto the second mobile device contained in the received second mobilemessaging service message.
 12. The application server of claim 11,wherein the first messaging service short code assigned to the oneapplication service, the second messaging service short code assigned tothe first provider, and the third messaging service short code assignedto the second provider are different from each other.
 13. Theapplication server of claim 8, wherein execution of the program causesthe central processing unit to operate the application server to performfunctions further including functions to: receive a third mobilemessaging service message from the server of the first provideraddressed to the first mobile device, the third message containing thesecond messaging service short code for the server of the first provideras the source address of the third mobile messaging service message;replace the second messaging service short code for the server of thefirst provider with the first messaging service short code of the oneapplication service, as the source address of the third mobile messagingservice message; forward the third message for routing through thewireless mobile communication network to the first mobile device;receive a fourth mobile messaging service message from the server of thesecond provider addressed to the second mobile device, the fourthmessage containing the third messaging service short code for the serverof the second provider as the source address of the fourth mobilemessaging service message; replace the third messaging service shortcode for the server of the second provider with the first messagingservice short code of the one application service, as the source addressof the fourth mobile messaging service message; and forward the fourthmessage for routing through the wireless mobile communication network tothe first mobile device.
 14. An article of manufacture, comprising: anon-transitory machine readable storage medium; and programminginstructions embodied in said medium for execution by at least onecomputer, wherein execution of the programming instructions configuressaid at least one computer to perform functions for processing mobilemessaging service messages relating to one application service for aplurality of mobile devices where the one application service isavailable from servers of a plurality of application service providers,including functions to: receive a first mobile messaging service messagefrom a first mobile device routed through a wireless mobilecommunication network based on a first messaging service short code ofthe one application service at least initially contained in the firstmessage as a destination address; based on identification of the firstmobile device, obtain a second messaging service short code for a serverof a first provider of the one application service; replace the firstmessaging service short code in the first message with the secondmessaging service short code for the server of the first provider as anew destination address for the first message; forward the first messagefor routing based on the second messaging service short code for theserver of the first provider as the new destination address of the firstmessage; receive a second mobile messaging service message from a secondmobile device routed through the wireless mobile communication networkbased on the first messaging service short code of the one applicationservice at least initially contained in the second message as adestination address; based on identification of the second mobiledevice, obtain a third messaging service short code for a server of asecond provider of the one application service, different from thesecond messaging service short code for the server of the firstprovider; replace the first messaging service short code in the secondmessage with the third messaging service short code for the server ofthe second provider as a new destination address for the second message;and forward the second message for routing based on the third messagingservice short code for the server of the second provider as the newdestination address of the second message.
 15. The article ofmanufacture of claim 14, wherein: identification of the first mobiledevice comprises a mobile directory number assigned to the first mobiledevice contained in the received first mobile messaging service message;and identification of the second mobile device comprises a mobiledirectory number assigned to the second mobile device contained in thereceived second mobile messaging service message.
 16. The article ofmanufacture of claim 14, wherein the first messaging service short codeassigned to the one application service, the second messaging serviceshort code assigned to the first provider, and the third messagingservice short code assigned to the second provider are different fromeach other.
 17. The article of manufacture of claim 14, whereinexecution of the programming instructions causes said at least onecomputer to perform functions further comprising functions to: receive athird mobile messaging service message from the server of the firstprovider addressed to the first mobile device, the third messagecontaining the second messaging service short code for the server of thefirst provider as the source address of the third mobile messagingservice message; replace the second messaging service short code for theserver of the first provider with the first messaging service short codeof the one application service, as the source address of the thirdmobile messaging service message; forward the third message for routingthrough the wireless mobile communication network to the first mobiledevice; receive a fourth mobile messaging service message from theserver of the second provider addressed to the second mobile device, thefourth message containing the third messaging service short code for theserver of the second provider as the source address of the fourth mobilemessaging service message; replace the third messaging service shortcode for the server of the second provider with the first messagingservice short code of the one application service, as the source addressof the fourth mobile messaging service message; and forward the fourthmessage for routing through the wireless mobile communication network tothe first mobile device.